Communications hub for crash event detection, response, and reporting system

ABSTRACT

A communications hub providing a repository of vehicle crash information communicated by a mobile communications device and of vehicle crash data records provided by crash event servicers, in a crash detection, response and reporting system that determines a possible crash event by periodically evaluating (a) changes in a motion signal and (b) crash sound indicators of one or more of (i) motor vehicle glass breakage, (ii) metal folding, (iii) contact thud, and (iv) tires screeching, and upon a failure to respond within a predetermined period to a notice of possible crash event, communicating an identifier and crash incident information to a dispatch center as first notice of loss for dispatching a response servicer and maintaining the repository to facilitate resolution of the claims arising from the vehicle crash event.

TECHNICAL FIELD

The present invention relates to apparatus and methods for responding tomotor vehicle crash events. More particularly, the present inventionrelates to data collection and communications management for motorvehicle crash event claims resolution with first notice of loss upondetecting the occurrence of a motor vehicle crash and responding andreporting the detection of the motor vehicle crash.

BACKGROUND OF THE INVENTION

In recent years, improved roadways, traffic control devices, and safetydevices that are installed and operated in motor vehicles have resultedin safer transportation by motor vehicle. Nevertheless, incidents andaccidents involving car and truck motor vehicles continue to occur.These include vehicle-to-vehicle collisions as well as single vehicleaccidents. While typically such incidents occur in locations whereresponse personnel may be readily directed to provide medical and towservices, some incidents involving disappearance of the motor vehicleand its operation occur (such as a single vehicle accident in which thevehicle leaves the roadway and becomes hidden from view in woods orwater).

Also, monitoring services seek “how am I driving” reports typically forfleet operators to monitor driving activities of vehicle operators butparents having children as new or inexperienced drivers also have becomeinterested in monitoring and reporting on motor vehicle operations.

While systems having GPS location tracking features and cellulartelecommunications devices have been installed in motor vehicles forcommunications between occupants and a tracking service provider, thereare drawbacks to such systems. The operator may be injured or blockedfrom initiating communications. Also, the operator may be using adifferent vehicle such as a rental vehicle.

Generally, motor vehicle accidents, whether of a single driver or of twoor more drivers, can be grouped as involving (i) low-speed, low-impactaccidents and (ii) higher-speed, higher-impact accidents. A low-speed,low-impact accident may occur in parking lots or even some roadwayevents. The motor vehicles involved generally remain drivable, anddrivers drive-away after an exchange of identification and insuranceinformation, and with, or sometimes without, a police response andinvestigation. Damages for property damage and personal injury in suchevents are typically resolved through assistance by the driver'sinsurance adjuster providing coordination of repair centers, interimrental replacement vehicles, and personal injury resolution.

Other accidents however, such as higher speed or higher impact crashevents, require responses by appropriate responders including police,emergency medical, and tow truck operators for accident investigation,medical care, and vehicle pull-outs such as from ditches or off-roadsites and for towing damaged un-drivable vehicles to an impound lot orstorage site pending disposition of the vehicle. Resolution of propertydamage, personal injury, and financial damages from such serious motorvehicles accidents, whether of a single driver or of two or moredrivers, involve more persons and interacting agencies than just thedriver(s). These persons and agencies include the insured policyholdersand respective insurance providers, but also include personal relatives,employer, fleet vehicle operators of a vehicle involved in the crashevent, tow dispatch and responding servicers, and repair and salvagefacilities. The occurrence of a motor vehicle accident typically leadsto activities by these other persons and agencies s to address andresolve the damages and losses arising from the accident.

The insurer and fleet operator (if such vehicle were involved) typicallyreceive notice of loss from the insured, and for low-speed drive-awayaccidents, such notice may be made some extended period afterward. Oftenthe damages and costs for resolution in such events are relatively low.However, in the more serious events such as a crash accident requiringdispatch and use of tow trucks, early notice of loss to the insurer andfleet operator is more important. The property damage and personalinjuries may be significant. The insurance provider and fleet operatorsin such crash events may seek accident and damages information includingon-site inspections for evaluating liability responsibilities, receiveand collect documentary materials such as accident reports, injury andmedical care invoices, vehicle damage inspection and repair/salvageevaluations, as well as providing claims adjustment services.

Adjustment services balance the needs of the policyholder and theinsurance carrier to make the policyholder whole yet minimize the costsand expenses involved in reaching resolution of the damages. Theadjustment service involves the collection and evaluation of largeamounts of documents and data from the various sources engaged inaccident resolution. The drivers may provide oral and written statementsto the insurer and to attorneys if the matter become litigious. Damagedvehicles are inspected, and repaired, at automotive repair body shopswith documented estimates providing a basis for repairs. In efforts tocontrol costs and streamline the repair process, some insurers suggestpolicyholders use insurer-approved repair facilities and accept use ofafter-market replacement parts (subject to warranties to thepolicyholder as to quality and reliability). In circumstances involvingtowed vehicles, the towing companies maintain information as to vehiclelocation and disposition, with movement and storage of the vehiclesubject to approvals of the vehicle owner. Evaluations may lead to afinding that the vehicle is not economically repairable, and the vehiclemay be designated for salvage. In the interim, rental vehicles incurcosts covered by the insurer or vehicle owner. The insurers seek timelyand quick dispositions to reduce costs and expenses arising from theadjustment and resolution of the damages from the crash event. In somecircumstances, investigators inspect crash event sites and vehicles tocollect accident information as to possible causes and damages. Also,various government agencies may seek crash event information such as forevaluating motor vehicle defects and to improve vehicle anddriver/occupant safety in travel. Communications and documentationinvolved in after-event information collection and event resolutioninclude written documents and correspondence, more recently inelectronic form such as emails, voicemail recordings, police and otherinvestigator reports, images of the crash event site and vehiclesincluding still frame photographs (electronic and paper) and video,relevant components of or the actual motor vehicle itself, and otherinformation, evidence, and reports relating to the crash event.

Accordingly, there is a need in the art for an integrated system andmethod for data collection and communications management for motorvehicle crash event claims resolution with first notice of loss upondetecting the occurrence of a motor vehicle crash and responding andreporting the detection of the motor vehicle crash. It is to such thatthe present invention is directed.

BRIEF SUMMARY OF THE INVENTION

The present invention meets the needs in the art by providing acommunications hub providing a repository for resolution of undrivablemotor vehicle crash events, comprising a plurality of mobilecommunications devices, each associated with a respective one of theplurality of drivers and configured with a sensor that generates amotion signal responsive to motion of the mobile communications deviceand a sound receiver for receiving a sound signal of sound proximate themobile communications device. The mobile communications deviceconfigured with software instructions that upon execution monitors foran occurrence of a crash event by periodically interrogating (a) themotion signal to determine whether a change in motion exceeds apredetermined motion threshold and or (b) the sound signal to determinewhether a sequence of sensed sound signals within a predetermined periodmatches crash sound indicators of one or more of (i) glass breakage,(ii) metal folding, (iii) contact impact, and (iv) tires screeching.Each mobile communications device comprising a display that upondetermining the occurrence of the crash incident displays a possibleevent window for selection of one of (a) to return the mobilecommunications device to monitoring for the occurrence of the crashincident and (b) to confirm the crash incident. The mobilecommunications device, upon (a) confirmation of the crash incident or(b) upon a failure of selection of one of the selectable options withina predetermined period, the mobile communications device communicatingby a communications network an identifier associated with the mobilecommunications device and crash incident information of a location data,date and time to the tracking and dispatch center. The tracking anddispatch center having a computer processor configured with anelectronic memory device that maintains driver information of drivername, address, insurance servicer and policy number for each of theplurality of drivers and further comprising for each mobilecommunications device a repository of: (i) vehicle crash incidentinformation communicated by the mobile communications device andassociated with a motor vehicle; and (ii) one or more vehicle crash datarecords, each said vehicle crash record containing data provided by oneof a plurality of crash event servicers. The plurality of crash eventservicers comprising (a) at least one response servicer for dispatchingby the tracking and dispatch center to a site of the crash incidentbased on the location data, the response servicer providing an imagingdevice and a communications device, whereby images received by theimaging device communicate by the communications device through thenetwork to the tracking and dispatch center for recording in therepository; and (b) a claims servicer that receives from the trackingand dispatch center notice of the identifier and crash incidentinformation, the claims service center configured for servicing aninsurance claim arising from the crash event using the vehicle crashincident information and the vehicle crash data records communicated tothe tracking and dispatch center and recorded in the repository.

In another aspect, the present invention is directed to a comprehensivecrash event and claims servicing system, comprising a telecommunicationsnetwork and a communications hub having a transceiver for receiving andcommunicating through the network crash event information from at leastone crash event servicer and maintaining said crash event information inan electronic database operatively engaged with the communications hub.A crash event notifier communicates a notice of a possible crash eventto the communications hub to initiate a crash event file for maintainingthe crash event information associated with the crash event. The crashevent notifier comprises one of a crash event detector device, a crashevent SDK imbedded in a consumer software application operated by aninsurance carrier, a motor club servicer, a cell phone network provider,a motor vehicle OEM monitoring servicer, a telecommunications report, atowing dispatch servicer, and a towing service provider (private ormunicipal). The crash event file associated with an identifierassociated with the notice of the crash event, whereby said informationis accessible for resolution of personal and property claims arisingfrom the crash event.

In another aspect, the present invention provides a method of resolvingclaims arising from undrivable motor vehicle crash events via acommunications hub repository service, comprising the steps of:

-   -   (a) providing a plurality of mobile communications devices, each        associated with a respective one of the plurality of drivers and        configured with a sensor that generates a motion signal        responsive to motion of the mobile communications device and a        sound receiver for receiving a sound signal of sound proximate        the mobile communications device;    -   (b) configuring the mobile communications device with software        instructions that upon execution monitors for an occurrence of a        crash event by periodically interrogating (i) the motion signal        to determine whether a change in motion exceeds a predetermined        motion threshold and or (b) the sound signal to determine        whether a sequence of sensed sound signals within a        predetermined period matches one or more crash sound indicators        of (i) glass breakage, (ii) metal folding, (iii) contact impact,        and (iv) tires screeching;    -   (c) upon determining by a respective mobile communications        device the occurrence of the crash incident, displaying thereon        a possible event window for selection of one of (i) to return        the mobile communications device to monitoring for the        occurrence of the crash incident and (ii) to confirm the crash        incident;    -   (d) upon (i) confirmation of the crash incident or (ii) upon a        failure of selection of one of the selectable options within a        predetermined period, communicating by the mobile communications        device within a communications network an identifier associated        with the mobile communications device and crash incident        information of a location data, date and time to a tracking and        dispatch center having a computer processor configured with an        electronic memory device that maintains driver information of        driver name, address, insurance servicer and policy number for        each of the plurality of drivers;    -   (e) receiving and storing in a repository of the tracking and        dispatch center,    -   vehicle crash incident information communicated by the mobile        communications device and associated with the motor vehicle; and    -   one or more vehicle crash data records, each said vehicle crash        record containing data provided by one of a plurality of crash        event servicers;        -   the plurality of crash event servicers comprising:        -   (i) at least one response servicer for dispatching by the            tracking and dispatch center to a site of the crash incident            based on the location data, the response servicer providing            an imaging device and a communications device; and        -   (ii) a claims servicer;    -   (f) communicating by the communications device images received        by the imaging device through the network to the tracking and        dispatch center for recording in the repository; and    -   (g) servicing by the claims service center an insurance claim        arising from the crash event using the vehicle crash incident        information and the vehicle crash data records communicated to        the tracking and dispatch center and recorded in the repository.

In yet another aspect, the present invention provides a method ofservicing claims with a comprehensive crash event and claims servicingsystem, comprising the steps of:

(a) providing a telecommunications network;

(b) establishing a communications hub with a transceiver for receivingand communicating through the network crash event information from atleast one crash event servicer and maintaining said crash eventinformation in an electronic database operatively engaged with thecommunications hub;

(c) communicating from a crash event notifier upon determination of acrash event, notice of the crash event to the communications hub toinitiate a crash event file for maintaining the crash event informationassociated with the crash event, said crash event file associated withan identifier associated with the notice of the crash event,

wherein the crash event notifier comprises one of a crash event detectordevice, a crash event SDK imbedded in a consumer software applicationoperated by an insurance carrier, a motor club servicer, a cell phonenetwork provider, a motor vehicle OEM monitoring servicer, atelecommunications report, a towing dispatch servicer, and a towingservice provider (private or municipal); and

(d) providing access to said crash event information for resolution ofpersonal and property claims arising from the crash event.

Objects, advantages, and features of the present invention may bereadily determined upon a reading of the following detailed descriptionin conjunction with the drawings and the appended claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a schematic overview of an illustrative embodiment ofa crash detection, response, and reporting apparatus in accordance withthe present invention.

FIG. 2 illustrates a process flow of an exemplary embodiment of anapplication for a mobile computer device configured for crash detection,response and reporting in accordance with the present invention.

FIG. 3 illustrates a screen image for operating the crash detection,response and reporting application.

FIG. 4 illustrates a screen image during monitoring the operation of thecrash detection, response and reporting application.

FIG. 5 illustrates a crash detected screen displayed when the crashdetection, response and reporting application determines that a possiblecrash event may have occurred.

FIG. 6 illustrates a screen image following detection of a possiblecrash event by the crash detection, response and reporting application.

FIG. 7 illustrates a screen image of the crash detection, response andreporting application after a request for assistance.

FIG. 8 illustrates a second screen image of the crash detection,response and reporting application after a request for assistance.

FIG. 9 illustrates a schematic diagram of an integrated system andmethod for data collection and communications management via acommunications hub for motor vehicle crash event claims resolution withfirst notice of loss upon detecting the occurrence of a motor vehiclecrash and responding and reporting the detection of the motor vehiclecrash.

FIG. 10 illustrates a detailed schematic diagram of communications hubof the integrated system and method for data collection andcommunications management for motor vehicle crash event claimsresolution illustrated in FIGS. 1 and 9 with first notice of loss upondetecting the occurrence of a motor vehicle crash and responding andreporting the detection of the motor vehicle crash.

FIG. 11 illustrates a tow vehicle provided by crash event responderequipped with a plurality of imaging devices for memorializing crashevent actions.

DETAILED DESCRIPTION

With reference to the drawings, in which like parts have like referencenumerals, FIG. 1 illustrates a schematic overview of an illustrativeembodiment of a crash detection, response, and reporting apparatus 10 inaccordance with the present invention. The apparatus 10 supports motorvehicle insurance and tracking services for drivers of motor vehicles 12with a computer software application 14 configured for crash detection,response and reporting operable on a mobile communications device 16.The mobile communications device 16 includes a microprocessor device,communications module, and display. The mobile communications deviceincludes, but is not limited to cellular telephone, tablet computer,laptop portable computer, or other similar microprocessor deviceconfigured with an operating system, information input devices (mouse,keyboard, touchscreen, actual or virtual), and a display device forpresentation of information during operation of the application. Forexample, the possession of cellular telephones is becoming moreprevalent. The application 14 resident on the cellular telephone in thepossession of the driver during motor vehicle operation, and operatingin a background mode, provides a passively present crash detection,response, and reporting feature for drivers as well as others having aninterest in the status of the driver and the motor vehicle. The mobilecommunications device 16 includes conventionally an accelerometer 17 afor detecting changes in linear acceleration and alternatively agyroscope 17 b (one or more axis) configured for detecting changes inangular rotation of the device. The accelerometer 17 a and the gyroscope17 b detect changes in motion of the mobile communications device andthus may indicate changes in the status of the motor vehicle (i.e.,especially a potential crash based on rapid changes in accelerationand/or rapid changes in angular rotation). The application 14periodically interrogates and determines changes in motion of the mobilecommunications device (acceleration and/or angular rotation) bycommunicating with, and receiving one or more motion signals from, theaccelerometer 17 a and from the gyroscope 17 b. In an alternateembodiment, the accelerometer 17 a and/or gyroscope 17 b may be aseparate device installed in the motor vehicle, which communicate withthe mobile communications device 16.

The apparatus 10 includes a central tracking/dispatch center 18, with acomputer server or processor 20. The computer server 20 includesconventional memory or storage devices and is configured for maintaining(adding, updating, revising) a database 21 with information retained onthe storage device. The database 21 of the tracking/dispatch center 18receives and stores the motion information and the sound signals onwhich the crash incident was determined, upon communication from themobile communications device of such information and signals through acommunications network. Further, the database maintains driverinformation of driver name, address, insurance company and policy numberfor a plurality of drivers and maintains vehicle crash information ofmotor vehicle, crash location data, date and time, and optionally one ormore sequences of sounds from a crash location, one or more imagesthereof, for a plurality of crashed motor vehicles. The computer server20 is further configured for analyzing and reporting on the status ofmotor vehicles having information tracked though the database of thecentral tracking/dispatch center 18.

The apparatus 10 includes one or more response services. These may beindependent service providers or dependent providers related to thecentral tracking/dispatch center 18. The illustrated embodiment includesa plurality of tow truck service/features 22 as a response service. Theresponse service includes a tow truck 22 and a portable lanterncamera/communications device 24. The portable lantern device 24 includesa high-wattage light 25, a camera 27, and a communications device 29.The light 25 is selectively operable for night illumination. The camera27 operates in video or still modes for imaging of the crash event, thesite, the motor vehicle(s) involved, and creating other picturedocumentation related to the crash event. The communications device 29provides two-way communications, such as cellular, WIFI, radio, orother, for communicating with the persons involved in the crash event,with the central tracking/dispatch center 18, with the tow serviceprovider, or others as appropriate. Live images may be transmitted asappropriate, for example, but not limited to emergency care and servicesproviders or the dispatcher 18. In the illustrated embodiment, the towtruck 23 optionally includes digital video recording andtelecommunications equipment 19 (i.e. MDVR and multiple cameras) forcommunicating images to the server 20, as well as capturing multiplevideo images from the tow truck and from the portable lantern camera 24that communicates with and through the telecommunications equipment. Inyet another alternate embodiment, the lantern camera/MDVR 24 providesthe on-site imaging functionality and there is no MDVR equipment mountedon the truck except for other wireless cameras carried, for example, inthe truck or by other responders, which communicate through the lanterncamera/MDVR 24 to the server 20. In an alternate embodiment, theportable lantern device 24 may be embodied in mobile communicationsdevice such as a cellphone equipped with a light emitting device, avideo imager, and a transceiver device for cellular networkcommunications, and a microprocessor. The microprocessor is configuredwith a software application for selectively activating the imager forreceiving images (video or separate image) of a crash site, storing theimages and selectively communicating the images through the network toreceiver. The light provides lighting for night activities at a crashsite.

The apparatus 10 further includes a claims servicer 26 that providesmotor vehicle claims information and processing services to insurancecarriers and motor vehicle owners and operators such as fleet operators.

The application 14, dispatch 18, ISP (independent service provider) 22,and the insurance claims servicer 26 communicate through acommunications network generally 30 including wireless, cellular,telephony, radio (two-way), world wide web communications devices andconnections, and other suitable electronic communications devices.

The server 20 is configured with the database 21 for tracking motorvehicles and drivers registered with the service, through a fleetoperator, an insurance company as a service for its insured, orindependently such as parents of young drivers. Further, the apparatus10 may gainfully be used by a fleet operator as an independent separatesystem.

FIG. 2 illustrates a process flow 50 of an exemplary embodiment of theapplication 14 operable with the mobile communications device 16 forcrash detection, response and reporting in accordance with the presentinvention. The driver initiates 52 operation of the application 14. Theapplication 14 may operate in a background mode of the mobilecommunications device so that other routine uses of the mobilecommunications device 16 (such as cellphone calls, internet access,email receiving and transmitting, mapping and routing directions, andother conventional uses) may proceed.

The application 14 monitors 54 for indicators of a crash event. In theillustrative embodiment, detection of motion above a preset speed causesthe application 14 to commence the crash detection monitoring functions.The mobile communications device 16 includes conventionally theaccelerometer 17 a, and the application 14 periodically interrogates theaccelerometer by communicating with, and receiving an accelerationsignal from, the accelerometer. An alternate embodiment includes thegyroscope 17 b that detects changes in angular rotation. The application14 in this embodiment periodically interrogates the gyroscope 17 b forreceiving angular rotation signals indicating rapid rotation of themobile communication device (for example, rolling over of a motorvehicle). The mobile communications device 16 includes a sound receiveror microphone.

The crash indicators include the motor vehicle motion signal and thesounds 58 received proximate the mobile communications device 16. Themotion signal may be the acceleration 56 signals, the angular rotationsignals 57, or both. The application 14 periodically receives 60 themotion information of the motor vehicle from the force monitoring deviceor accelerometer and alternatively the angular rotation signals 57 fromthe angular rotation measuring device. The application 14 also receivesaudio signals though the microphone. The audio signals include crashsounds which more particularly include glass breakage, metal folding,contact impact sound—a “thud” of vehicle-to-vehicle or vehicle-to-objectsound, and screeching of tires for example skids from locked brakes orlateral pushing of a vehicle. Rapid declaration, rapid changes inrotation, and crash sounds (glass breakage/metal folding/contactthud/screeching of tires) indicate a possible crash event. A crashindicator database 62 provides accident or crash event correlated motionand crash event sound thresholds. The information is processed 64 andcompared with standards maintained in the database 62 to determine 65whether a possible crash event has occurred. If not, the apparatuscontinues monitoring 66 for crash event signals. The use of multipleindicators of a crash event facilitates reduction of false alarms.

Monitoring crash event indications 54 involves detecting sounds with amobile device microphone that exceed a respective predeterminedthreshold for one or more of the glass breakage/metal folding/contactthud/screeching of tires sounds, detecting changes in acceleration with3-axis (x, y, z) accelerometers that exceed a predetermined threshold,and/or detecting changes in angular rotation that exceed a predeterminedthreshold. Upon detecting one or more high threshold events, theapplication 14 may check a GPS-based speed for evidence that the mobilecommunications device is slowing or rotating rapidly or has stoppedmoving. If the GPS-based speed is unchanged, the application 14 wouldreject 82 the detected event and return to crash monitoring 54. If theGPS-based speed indicated slowing/rotation/stopping, the processing ofthe sound and motion recording files, which would include recording fora predetermined period of pre-event sound and motion information andpost-event recording of such information for a second predeterminedperiod.

In an illustrative embodiment, the application 14 maintains a continuousrecording database of the motion and audio signals received duringmonitoring. The database is configured for maintaining a lead portion(pre-event) of a predetermined period preceding the possible crash eventand a trailing portion (post-event) of a second predetermined periodpost-possible crash event. The recorded database uploads to the centraltracking/dispatch center 18 during notification communication of apossible crash event to the central tracking/dispatch center 18. Thedatabase 21 of the tracking/dispatch center 18 receives and stores themotion information and the sound signals on which the crash incident wasdetermined, upon communication from the mobile communications device 16of such information and signals through a communications network 30.Further, the database 21 maintains driver information of driver name,address, insurance company and policy number for a plurality of driversand maintains vehicle crash information of motor vehicle, crash locationdata, date and time, and optionally one or more sequences of crashsounds from a crash location, one or more images thereof, for aplurality of crashed motor vehicles.

If the application determines 68 that a possible crash event hasoccurred, the application alerts 70 the driver. Determination of apossible crash event in the illustrative embodiment involves both soundand motion crash indicators being determined as true (i.e., exceedingrespective predetermined thresholds). An exceeded sound threshold aloneor an exceeded acceleration threshold alone or an exceed angularrotation alone may be rejected as indicating a crash event andprocessing would return to monitor 54. The combination may indicate acrash event. The alert 70 presents a visual message 104 (see FIG. 5) ona display of the mobile communications device 16. The alert 70 mayinclude an unmistakable audio tone at high volume to draw the driver'sattention to the mobile communications device 16. The driver may respondin the negative and the application 14 then returns to the monitor 54processes. If the driver confirms the crash event, the applicationpresents 72 selective choices for calling 911 or emergency contact,contact the insurance carrier, request roadside assistance, or cancel,as discussed below in reference to FIG. 6.

If the driver does not respond 72 after a predetermined period of time(for example, but not limitation, a period of 60 seconds), theapplication 14 initiates assistance. This includes notification toemergency centers (such as to local police authorities) 74, notification76 to the central tracking/dispatch center 18, and initial accidentnotification 78 to the claims service center 26. The application mayalso evaluate 80 whether the accelerometer and sounds information shouldbe uploaded to the crash indicator database.

The driver, upon being alerted to the possible crash event, mayselectively respond for the system to ignore 82 the possible crash event(i.e., no crash event occurred); or 83 to initiate 84 telephone contactwith appropriate local police authorities; to contact the insurancecarrier 85 or to request 86 assistance. The application provides updates88 to the driver as to the status of the requested assistance. Suchupdates for example, may include contact information for a tow truckoperator and arrival time. The driver may select to cancel 89 thenotifications and processing of crash event services by the application14.

The application 14 accordingly synchronizes the crash event with themotorists, the date and time of crash event, the place of the crashevent, and the severity of the crash event. This information provides abasis for accident reconstruction, predictive indications of potentialloss and injury, and also perfects the validity of the report of thecrash event by the motorist involved while supporting officialinvestigative reports. The detected and recorded motion information(i.e., the acceleration signal and the angular rotation signal) provideadditional information useful for accident reconstruction evaluations.

FIG. 3 illustrates a screen image 100 for operating the crash detection,response and reporting application 14 on the mobile communicationsdevice 16. The application 14 displays an activate button 102. Operatingthe button 102 causes the application 14 to operate in the background ofthe mobile communications device 16, monitoring for a possible crashevent, and responding appropriately, as discussed above. It is to beappreciated that the initiate screen 100 (and the monitoring screen 110(FIG. 4) are in an exemplary embodiment of a stand-alone application. Aproduction application in an alternate embodiment such as provided tocustomers of an insurance provider, may embed the application 14 withina hosting application for the insured of the insurance provider or asimilar hosting application with other consumer-facing features andservices of the provider (for example, display a report of policy termsand limits, provide for changes to policy coverage, add, delete ormodify driver and motor vehicle information, and other insuranceservicing features.)

FIG. 4 illustrates the monitoring screen 110 that may be displayedduring the monitor processing of the crash detection, response andreporting application 14. The screen 110 includes a status window 111.The status window displays a short descriptive phrase as to the statusof the application 14 shown in Table 1 below:

TABLE 1 Status Window Phrases Phrase Definition Crash Sensing - theapplication 14 is monitoring for a possible Monitoring crash event CrashDetected - the application 14 detects sound and motion Triggeredinformation indicating a crash event may have occurred Crash Sensing - acrash event has occurred; the application 14 Confirmed provides actionoptions for selection by the driver Crash Sensing - the crash event hasbeen reported and status of Reported action options and of responseservicers are displayed

The window 111 in FIG. 4 indicates that the application 14 is monitoringfor a possible crash event. The application 14 monitors sound events andmay provide a real-time signal display 112 on the screen 110. Further,the screen 110 displays 114 the three-axis acceleration of the motorvehicle. A cancel button 116 causes the application to cease operating.An “in-accident” button 118 enables the driver to initiate crash eventprocessing by the application 14, including notification to the centraltracking/dispatch center 18 that a crash event has occurred. In responseto the “in-accident” button 118, the application 14 communicates crashinformation, vehicle information and driver information using thecommunications of the mobile communications device 16. A window 119displays the driver and vehicle information. Alternatively, the displaymay present a graphic (not illustrated) of the motor vehicle based onthe detected changes in the angular rotation of the mobilecommunications device 16.

FIG. 5 illustrates a crash detected screen 103 displayed when theapplication 14 determines that a possible crash event may have occurred.The screen 103 may be accompanied with an unmistakable audio tone athigh volume to draw the driver's attention to the mobile device. Thescreen 103 displays a possible event window 104 that includes the time104 a and GPS coordinates 104 b as well as the vehicle information 119window. The screen 103 includes a “no accident-disregard” button 106 andan accident confirmation button 105 with text “Yes, I was in anaccident.” The driver operates the “I was in an accident” button 105 toconfirm the detection of a crash event. The driver operates the “noaccident-disregard” button if the detection was incorrect as no crashincident had occurred.

The “I was in an accident” button 118 shown in FIG. 4 is forcircumstances where the driver wants to proceed manually to report acrash event without the application detecting the crash event; FIG. 5provides the confirmation “accident” button 105 for the driver toconfirm that the detection of the crash event by the application wascorrect. Both buttons 118 and 105 cause the application 14 to proceed tocrash event processing in reference to FIG. 6. The“no-accident-disregard” button 106 causes the application 14 to returnto the monitoring screen 110 and monitoring as shown in FIG. 4.

FIG. 6 illustrates a screen 120 displayed to the driver on the mobilecommunications device 16 following detection of a possible crash eventby the crash detection, response and reporting application 14. Thewindow 111 in FIG. 6 indicates that the application 14 acknowledges orconfirms receiving the crash event notice following the use of theconfirm button 118. The screen 120 includes an insurance window 122 thatdisplays the name and address of the insured; the make, model andvehicle identification number of the insured motor vehicle; and theinsurance carrier and policy number. The screen 120 provides selectivelyactuated buttons to direct the activities of the application 14. A“call” button 123 causes the application 14 to imitate a telephone callto the insurance carrier. A “cancel” button 124 directs the applicationto resume monitoring for a possible crash event. The application 14notifies the central tracking/dispatch center 18. A “call 911” button126 directs the application 14 to initiate a telephone call to localemergency services such as local police and ambulance services.

A “request assistance” button 128 initiates services from independentservice providers 22. In the illustrated embodiment, the independentservice provider 22 is a roadside assistance service. The application 14communicates this request to the central tracking/dispatch center 18.The information communicated by the application 14 includes the vehicleidentification number, the driver information and contact phone number,and the location, time, and event. A crash event window 129 displayscrash event information including the report time, the location of thecrash event (address, if determined), a geographical coordinatedesignation, and crash severity. The “cancel” button 124 cancels thereporting and status monitoring activities. Appropriate information forcancelation communicates from the mobile communication device 16, suchas to the tracking/dispatch center 18 and/or the service provider 22.

FIG. 7 illustrates a screen 130 of the crash detection, response andreporting application 14 after a request for assistance is selected. Thewindow 111 in FIG. 7 indicates that the application 14 has reported thecrash event. The screen 130 displays the insurance window 122 and thecrash information window 129. Optionally, the screen 130 may display thetime of detection of the crash event and the time the crash event wasreported to the central tracking/dispatch center 18. The screen 130includes an update field 134. The application 14 presents in the updatefield 134 the status of the requested assistance. This includes the type136 of assistance requested, the time 138 the request was made, and thestatus 140 of the response. The screen 130 may include an initiateemergency call button 137. A cancel assistance button 139 communicates acancellation notice to the independent service provider 22 and to thetracking/dispatch center 18.

FIG. 8 illustrates a second screen 150 of the crash detection, responseand reporting application after a request for assistance, depictingupdated assistance information 152. This may include the time ofdispatch 154 and an estimate time of arrival 156. The update field mayalso present (not illustrated) the contact information of the tow truckdriver. A call button 157 initiates telephonic communication with theoperator of the tow truck. Optionally, a confirm arrival button enablesthe driver to communicate status information to the tracking/dispatchcenter 18. A cancel button 159 communicates a cancellation notice to theindependent service provider 22 and to the tracking/dispatch center 18.

Although not illustrated, the application 14 includes user setup screensfor entry of driver and vehicle information. This information includesthe driver name and address, insurance company and policy, and thevehicle identification number and make and model. The informationuploads to the database 21 on the server 20. The native application,downloaded and installed on the mobile communications device 16,maintains background processes such as environmental monitoring thatoccurs. The environmental conditions for monitoring may be selectedthrough appropriate control screens. For example, environmentalmonitoring may occur under conditions which correspond to the userdriving or riding in a moving vehicle above a specified speed (e.g. 5mph). Optional detection of known vehicle RF emitters (e.g. BT or WiFi)may be used to enhance recognition of in-vehicle operation. That is,detection of RF signals may cause the application 14 to commencemonitoring. In an alternate embodiment, the application 14 operates froma selection button provided through a hosting application such asprovided as an SAAS web site of an insurance carrier or fleet operator.

As discussed above, the environmental monitoring includes periodicallyreceiving and evaluating x, y, z accelerometer outputs and/or gyroscopeaxis output (such as accelerometer or gyroscope devices embodied in themobile communications device 16) and microphone (e.g. engine sounds,ambient sounds, crash sounds) for communication of sounds for analysisof possible crash events. In addition, the application may receive motorvehicle speed signals (either GPS or handset-based cellular assisted)and configured for translating to approximate vehicle x, y, zcoordinates and thus speed and angular rotation.

A determination of a significant possible crash event may be made upondetection of multiple ambient conditions, such as: high negativeacceleration in the motor vehicle x or y axis, rapid negative change invehicle speed, high or rapid changes in angular rotation, and crashsounds corresponding to vehicle impacts. An alternate embodimentincludes spectral analysis for sounds of glass breaking and metalshearing, bending, folding, or otherwise experiencing high impactchange, impact thud, and tire screeching in the possible crash eventdetermination. The determination is made based on a reasonable match ofsounds from the event with sounds from known crash events. Suchinformation may be maintained in a crash indicators database.

Upon determination 65 of a significant possible crash event, actions maybe initiated (automatically or selectively) which may include:

a. Prompting 70 the mobile communications device 16 via screen message104 and notification sound requesting driver confirmation 105, 106whether a crash event has occurred and whether the driver wants to placean emergency 911 call.

b. If the user confirms a crash, the application may immediately send 83a message to third-party for roadside assistance initiation and to thetracking/dispatch center 18.

c. If the user does not respond to the application notification (e.g.because the driver is injured or otherwise unable to respond), theapplication may prompt the driver with an audible message to confirmverbally to call 911 via voice command. Optionally, the application maybe configured to include the user/driver opting into an automatic crashnotification feature which activates a speakerphone-based 911 call topermit a 911 operator to interrogate the driver hands-free.

Upon initiation of the roadside assistance call, the application 14 maybe used to communicate the status of roadside assistance response. Thisfeature may be subject to the level of integration with the roadsideassistance company or other service provider.

The application of the present invention provides improved reporting ofmotor vehicle accident and crash information to persons having interestin the driver status (such as, parents, central tracking/dispatch, fleetoperators, and others), while providing early initiation and firstnotice to the insurance claim service of the crash event, and providingdispatch of independent service provider services 22 such as tow truckservices, though a machine-to-machine monitor, tracking, andnotification system. The first notice available through the monitor,tracking, and notification system facilities claims processing byproviding the identification of the insured motorist, the motor vehicleinvolved, the location of the vehicle and the crash event, and updatesof the status. Further, the application in an alternate embodimentincludes video/photo recording features following detection/confirmationof a crash event. This enables the driver to generate video/photo imagefiles that may automatically upload to the tracking/dispatch center 18and servers 20 to complement or substitute for tow truck-generatedvideo/photo information.

In an alternate embodiment, the mobile communications device 16 may beconfigured for determining whether the device is in the hands of thedriver or passenger. This may be determined in various way, includingmonitoring the accelerometer 17 a and/or the gyroscope 18 b as therotation sensor, the use of the touchscreen of the device, use oractivity of another software application operative with the mobilecommunications device, and monitoring for excessive speed or braking asindicative of driving issues. For example, the application may accesscommercial routing software to determine the legal speed limit on roadand compare such with the actual speed of the motor vehicle in which themobile communications device is carried. Alternatively, the monitoringconfiguration may use other of the device's sensors, such as the camera,to determine where the device is relative to the driver's seat orsteering wheel of the vehicle. Yet alternatively, the application 14 maybe configured to use the inertial sensor data to determine handheld useof the mobile communications device 16 while driving, for initiatingwarnings or alerts to the driver. Alternatively, the configuration mayincorporate a comparison of RF patterns from the vehicle operationassociated previously with the driver to determine differentialoperation. If the application 14 determines the mobile communicationsdevice 16 is within the hands of the driver, or is being operated by thedriver, an alert may be provided as to inappropriate or prohibiteddriver behavior (e.g. texting, excessive speed and braking, erraticdriving, etc.). Further, a fleet operator may be notified, for example,after repeated alerts to the driver, which alerts may include entries toa driver's operation history maintained by the fleet operator orescalated actions up to an including warnings and notifications thatdriving privileges are being revoked. In such matters, a driver may needto complete an in-house fleet operator curriculum or tutorial on motorvehicle safety operations in order to restore driving privileges onbehalf of the fleet operator. If the driver is entering data (e.g. textmessage, updating apps, etc.), an audio and visual warning to the drivercould be made to discontinue while driving.

With reference to the drawings and FIGS. 1 and 2, the system 10 detectsthe crash of the motor vehicle with crash detection device carried withthe motor vehicle for crash response and reporting. The driver (orpassenger) carries or brings into the motor vehicle the mobilecommunications device 16 configured with the sensor that generates themotion signal responsive to motion of the mobile communications deviceand a sound receiver for receiving a sound signal of sound proximate themobile communications device. The motion signal may be the accelerationsignal from the accelerometer 17 a, the angular rotation signal from thegyroscope 17 b, or both. The mobile communications device 16 configuredwith software instructions or application 14 that upon executionmonitors for an occurrence of a crash event by periodicallyinterrogating (a) the motion signal to determine whether a change inmotion exceeds a predetermined motion threshold and (b) the sound signalto determine whether a sequence of sensed sound signals within apredetermined period matches one or more crash sound indicators of (i)glass breakage, (ii) metal folding, (iii) contact impact, and (iv) tiresscreeching. A display that upon determining the occurrence of the crashincident displays a possible event window with a selectable option ofthe driver or passenger (a) to return the mobile communications deviceto monitoring for the occurrence of the crash incident or (b) to confirmthe crash incident. Upon a failure of selection of one of the selectableoptions within a predetermined period, communicating by thecommunications network 30 an identifier associated with the mobilecommunications device 16 and crash incident information including thelocation data to a tracking and dispatch center 18 having apre-registered record of the mobile communications device 16 andconfigured for receiving and storing the acceleration information andthe sound signals on which the crash incident was determined. Theservicer 22 dispatched by the tracking and dispatch center 18 respondsto the site of the crash incident based on the location data.

The claims service center 26 is configured for servicing an insuranceclaim arising from the crash incident as reported by the tracking anddispatch center 18. Additional incident services may be provided, suchas providing through the servicer 22 a transport vehicle fortransporting a damaged motor vehicle to the crash site and alsoproviding insurance claims process services for the motor vehicle owner,operator and insurer including documentation, images, and accidentincident details about the operation of the motor vehicle.

FIG. 9 illustrates in a schematic diagram an embodiment 180 of thepresent invention providing an insurance claims process services systemas an integrated system and method for claims resolution data collectionand communications management within a fleet vehicle system having afleet hub 182 for first notice of loss upon the detecting of theoccurrence of a crash involving motor vehicle(s) 12 and the dispatchtracking center 18 for responding and reporting generally 184 of themotor vehicle crash. The illustrated embodiment includes acommunications hub 186 for motor vehicle crash event claims resolution.The fleet hub 182 operates or monitors one or more motor vehicle usagesas a fleet of a plurality of motor vehicles. The fleet hub 182 maintainsa database 188 of motor vehicle information for each vehicle in thefleet, including equipment type, current travel schedule (from and tolocations, date, current location (GPS)), driver/operator informationassociated with the motor vehicle (name, contact information, andidentification number associated with the mobile communications deviceequipped with the crash event detection and reporting applicationdisclosed herein). The communications hub 186 includes a database 188that provides a central repository of data, facts, reports, information,videos, images, sounds, vehicle disposition, insurance coverage andclaims resolution relating to the crash event. The centralizedrepository includes the driver/operator information (name, contactinformation, identification number associated with the mobilecommunications device equipped with the crash event detection andreporting application disclosed herein, and insurance carrier 26information including coverage policy and carrier contact such as phonenumber and/or email address for notifications and for claims servicing)and contact information for registered related persons if any associatedwith the driver for example spouse and other relatives and fleetoperator if any. The communications hub 186 is configured for providingcommunications 192 to registered contacts of the driver and theinsurance carrier 26 as to the crash event. The registered contacts haveone or more contact identifiers such as office phone number, cellularphone number, email address or other identifier through which theregistered person may be contacted for communications. Thecommunications hub 186 also communicates as to vehicle dispositionstatus, for example, as illustrated with vehicle repair shop 194 butsalvage disposition as well, and with the tow service provider 22.

In continuing reference to FIG. 9, the communications hub 186 in analternate embodiment may be configured for vehicle disposition triageevaluation. The communications hub 186 may be configured for providingnear real time videos, pictures, text (reports), and/or audioinformation from the crash event site a vehicle disposition triage site187. The vehicle disposition triage site 187 applies the informationwithin an analysis protocol to assess and evaluate appropriatedisposition of the damaged vehicle and documenting information pertinentto the extent of damage for a resultant property damage claim. Further,the communications hub 186 supports a services monitoring center 189.The center 189 particularly monitors within the illustrated embodimentthe tow service provider for example in the preparation of crash eventand response incident and response performance reports summarizingrelevant crash information and services provided. These include incidentreports for example, determining and limiting a liability issueinvolving the tow service provider 22 in relation to tow truck operationand services. Similar support may be provided for other responderservices. The communications hub 186 further periodically performsquality checks to ensure proper operation on the video and relatedequipment on the tow trucks and the collected information may be usedfor incident reports pertaining to driver performance.

FIG. 10 illustrates a detailed schematic diagram of the communicationshub 186 of the integrated system 180 for data collection for the centralrepository database 190 and communications management for motor vehiclecrash event claims resolution illustrated in FIGS. 1 and 9 with firstnotice of loss upon detecting the occurrence of a motor vehicle crashand responding and reporting the detection of the motor vehicle crash.Particularly, the communications hub 186 provides insurance claimsprocess services generally 94 for the motor vehicle owner, fleetoperator (such as in the illustrated embodiment) and insurer includingaccident documentation, accident and vehicle images, accident incidentdetails about the operation of the motor vehicle, motor vehicledisposition (repair service 192 or salvage). The communications hub 186thereby provides a central repository for the parties involved in claimsresolution.

In that regard, the communications hub 186 communicates through atelecommunications network 196 with authorized servicers generally 198involved in responding to the crash event and supporting claimsresolution subsequent to the crash event. The servicers access thecommunications hub 186 through a portal such as an Internet web site.The portal provides conventional login security such as user name,password, second factor authentication, and encryption ofcommunications. The communications hub 186 maintains login informationfor authorized servicers 198, receives and stores accident event andsubsequent claims process documentation, and coordinates instructionsand responses among the servicers. The servicers include the responseservicer 22 for initial response and documentation generation at thecrash site, the disposition servicers that include the repair servicer194 and a salvage servicer 210, a rental servicer 212 for providingtemporary use of a motor vehicle for the policy holder 16. The insurancecarrier 26 includes a claims servicer 214 and may include an insuranceagent 216 for interacting between the policy holder and the insurancecarrier for insurance sales and service. Cargo damage and risk mayfurther involve communications with cargo insurer services 200 and sitecleanup and remediation may involve third party hazardous materialsservicers 202. These may be local fire department and rescue services orprivate commercial entities.

The communications hub 186 maintains the database 190 of driverinformation records 218 and of accident event information 220. Thedriver information records 218 includes the driver name 220, contactsinformation 222, insurance carrier information 224 and theidentification number 226 associated with the mobile communicationsdevice equipped with the crash event detection and reporting applicationfor the driver. The database 190 also collects and distributes toauthorized servicers 198 documentation 230 of the crash event, includingwritten documents such as email correspondence, letters, reports (forexample but not limited to police, accident investigator, analysts'reports, claims service reports, vehicle disposition, vehicle repairestimates, authorizations, and completions, salvage and disposition, andresolution documents including offers and settlement agreements). Thedatabase further receives and stores video files 232, photographs ordigital images 234 related to the crash event or persons involved, andmetadata 236 related to the crash event. The metadata particularlyincludes the data regarding the interrogated changes in motion of themobile communications device (acceleration and/or angular rotation).This data includes (a) the motion signal on which a determination ismade that a change exceeds a predetermined motion threshold and or (b)the sound signal on which a determination is made that a sequence ofsensed sound signals within a predetermined period matches one or morecrash sound indicators of (i) glass breakage, (ii) metal folding, (iii)contact impact, and (iv) tires screeching. In an alternate embodiment,the metadata may include motion signals for a first predetermined periodpreceding the determination as well as motion signals for a secondpredetermined subsequent to the determination.

FIG. 11 illustrates the tow vehicle 250 provided by a crash eventresponder, which tow vehicle is equipped with a plurality of imagingdevices 252 for memorializing crash event actions. The imaging devices252 mount to the tow vehicle for imaging forwardly 254, rearwardly 256,and opposing sides 258, 260. The opposing side imaging devicespreferably mount at an oblique angle 262 outwardly relative to alongitudinal side of the tow vehicle for imaging of passing vehicleslateral of the tow vehicle. The opposing side imaging devices may bemounted for mirror view images 258(a) and/or alternatively pylon view(258 b) proximate the side of the tow vehicle. Analysis of the sideimages may yield identification of vehicles having operators inviolation of traffic laws requiring reduced speed or “move over” spacingfrom the stopped tow vehicle present at the crash site. The analysis maybe made by viewing of the recorded drive-by images or with a computerassist or analyzer for extracting vehicle information (color, type,characteristics, license tag and other such information). Alternatively,the tow vehicle 250 may selectively include an in-cab imaging device 264and a winch imaging device 266. In an alternate embodiment, a tail endimage device 268 mounts to a support member disposed below a leadingedge of the flatbed platform of the tow truck. The image device 268faces rearwardly to image the extraction of the crashed motor vehicleand particularly the undercarriage for documenting undercarriage damagepost-crash event and prior to/during extraction.

The communications hub 186 of the present invention provides acentralized claims service center that receives a first notification ofloss notice from the tracking and dispatch center 22, such as may beoperated by a fleet hub 182, and thereafter receives, stores, and makesavailable information related to the crash event subject of the notice.The notice communicates from a crash event detector, such as thedisclosed application operative with the mobile communications device.The notification includes the identifier and information of the possiblecrash event. The communication hub 186 thereafter receives multimediainputs from one or more notice of loss information providers andservicers. The providers and servicers include the insured, theinsurance company, the insurance agent, repair shups, salvage or storageyards, and other interested entities. The communications hub 186 furthermay be configured in an alternate embodiment for servicing of one ormore insurance claim(s) for personal and property damage arising fromthe crash event.

The communications hub 186 acts as a “cradle-to-grave repository” orbeginning-to-end collector from commencement of collecting crashinformation upon notice, processing and maintaining crash eventinformation about the crash and resulting insurance claims (personal andproperty), to final resolution of the claims arising from the crashevent. The communications hub 186 may be independent providing servicesto fleet operators as well as for insurance carriers, or motor vehicleindustry operator involved in servicing motor vehicle crashes and/orinsurance claims resulting from said crashes. The communications hub 186provides a central facility with visibility into all activities involvedwith a crash and claims resolution. This includes initial crash responsebeginning with accident severity, pre-claim data and videos from theaccident site, consumer phone and written correspondence, vehiclelocation at all times, data from the adjustment process, vehicle repairand/or salvage information and other related data.

With reference to FIGS. 1 and 2, the system 10 in accordance with thepresent invention operates 52 for detecting a crash incident of themotor vehicle with crash detection response and reporting. The system 10provides (a) the plurality of mobile communications devices 12 eachcarried by a driver or passenger in the motor vehicle. Each mobilecommunications device 12 has the motion sensor (accelerometer 52 as anacceleration sensor and/or gyroscope as an angular rotation sensor) thatgenerates the motion signal responsive to motion of the mobilecommunications device 12 and the sound receiver for receiving a soundsignal of sound proximate the mobile communications device. The mobilecommunications device 12 is configured with software instructions thatupon execution monitors 54 (preferably in the background of theoperation thereof) for the occurrence of a crash event. The softwareinstructions are configured 64 for (b) periodically interrogating (a)the motion signal to determine whether the change in motion exceeds apredetermined threshold, (that is, of the accelerometer 56 to determinewhether a change in acceleration exceeds a predetermined accelerationthreshold and/or the gyroscope to determine whether a change in angularrotation exceeds a predetermined rotation threshold), and (b) the soundsignal to determine whether a sequence of sensed sound signals within apredetermined period matches crash sound indicators of (i) glassbreakage, (ii) metal folding, (iii) contact impact, and (iv) tiresscreeching. Then, (c) based on the interrogations of the motionsignal(s) and the crash sound signal, the mobile communications device12 determine 65 whether a crash incident occurred, and if so 68 thedisplay of the mobile communications device 12 alerts the driver 70 anddisplays a possible event window 104 (see FIG. 5) for selection by thedriver of one of (a) return 106 the mobile communications device tomonitoring 54 for the occurrence of a crash event and (b) to confirm 105the crash event. In one aspect the mobile communications device (d)makes an alert, which may be audible or visual. In response, (e)determining 71 whether the alert generated a crash response by thedriver through the mobile communications device, and if not, 72communicating a location data of the crash incident to a serviceprovider for response. For example, upon a failure of selection of oneof the selectable options within a predetermined period, the mobilecommunications device 12 communicating by a communications network 30 anidentifier associated with the mobile communications device and crashincident information of the location data, date and time to the trackingand dispatch center 18 for entry into the database 21. Further, thesystem 10 includes at least one response servicer 22 for dispatching bythe tracking and dispatch center to the site of the crash incident basedon the location data, the response servicer 22 providing the lanterndevice 24 having the light 25, the imaging device 27, and acommunications device 29, whereby images received by the imaging device27 communicate by the communications device 29 through the network 30 tothe tracking and dispatch center 18. The images may be video or singleframe. Further, (f) the tracking and dispatch center 18 communicating astatus of the service provider 22 response to the mobile communicationsdevice 12. Alternatively, the response servicer 22 may provide thevehicle transporter (tow truck 23) for vehicle pull-out or movement atthe crash site and for transport to a repair center or storage facility.The tow truck may include an electronic data storage device forcommunication with the imaging device and recording of images prior tocommunicating the recorded images to the tracking and dispatch center18.

An alternate embodiment includes alternative reporting and action pathfor commercial vehicle operators that addresses the difference inprocedures for motor vehicles and trucks used in cartage. For example,the third-party servicer may include cargo insurance carriers, emergencyresponse teams for tracking and fleet operators, hazardous materialshandling and clean-up services, salvage and similar such services. Suchembodiment provides for simultaneous reporting and alternate claiminformation streams.

With reference to FIGS. 9 and 10 in the illustrative embodiment, themobile communications device 12 communicates as a crash event detectordevice the interrogated changes in motion of the mobile communicationsdevice (acceleration and/or angular rotation) with the notice of thepossible crash event to the tracking and dispatch center 18. The motionsignal data, and in an alternate embodiment the motion data for thefirst predetermined period preceding the determination and alternativelythe motion date for the second predetermined period subsequent to thedetermination is received and stored as crash event metadata 236.

The first notice of loss may in alternate embodiments communicate from acrash event notifier 12 a to the communications hub 186 for originatinga file for the crash event within the central repository database 188.The notice may originate from one or more notifier 12 a as relatedentities including the insurance carrier, the driver involved, a motorclub organization, a tow provider, a crash event SDK imbedded in aconsumer software application operated by the driver or owner of themotor vehicle through an insurance carrier, a motor club servicer, acell phone network provider, a motor vehicle OEM monitoring servicer, aswell as originating after a telecommunications report (telephonic,email, facsimile, mail, or other communications mode), a towing dispatchservicer, and a towing service provider (private or municipal). Thus,the alternative first notice of loss notifiers may initiate the centralcommunications hub 186 actions and repository information collection,storage, and reporting, through OEM motor vehicle services such asONSTAR tracking service or similar, motor club dispatch and reportingservices (for example, AAA motor club of which the motor vehicleoperator is a member), third party crash detection device (using adongle configured for crash event detection operatively engaged to themotor vehicle data bus), other third party telematic systems, ormotorist communications (telephone, mail, email, SMS text) to a relatedassociated entity (employer, insurer, motor club service).

In the illustrated embodiment, the communications hub 186 communicateswith the response servicer 22 as to disposition of the motor vehicle,which servicer reports transport of the motor vehicle to a storage lot,or to a repair servicer 194. The movement and disposition may be made bya non-solution entity or a solution entity. Non-solution entitiesinclude the motorist, law enforcement personnel responding to the crashevent, out of network tow service provider, or other entity notaffiliated with the communications hub 186. A solution entity is one ofthe various entities associated with the communications hub 186. Theseinclude but not limited to tow service providers such as one trained andauthorized to make vehicle disposition assessments at the crash site.The disposition of the motor vehicle communicates to the communicationshub 186 for tracking disposition location and status within the database190. Alternatively, disposition may be determined by an appropriateauthorized vehicle triage evaluator such as personnel of the insurancecarrier, the motor vehicle owner, or other authorized third-partyservicer.

If an adjuster finds the motor vehicle unrepairable, the disposition ofthe motor vehicle to a salvage yard 210 may be expedited bycommunications through the communications hub 186. Such communicationsmemorialize documents 230 providing owner consent for transport anddelivery of the motor vehicle to the storage lot, the repair servicer194, or salvage 210, and related documents including adjuster reports ofdamage and repair costs, and insurance carrier agreement for repair orsalvage. Similarly, temporary motor vehicle may be provided by therental servicer 212 (whether owner paid or covered by insurance). Therental documents similarly are communicated to the database 190 of thecommunications hub 186 for storage and access as necessary by the motorvehicle owner and the insurance carrier 26.

The crash detection, response and reporting apparatus 10 according tothe present invention establishes, occupies, and provides an effectiveinterlinked network of a plurality of motor vehicles 12 each trackedlocally during motor vehicle operation by a microprocessor-basedapplication 14 that executes software code on the mobile communicationsdevice 16 of the driver, featuring communications networked driver/motorvehicle, central tracking/dispatch monitoring center 18, and attendantservices including claims servicer 26 for an insurance carrier andsupport features for drivers such as tow truck services 22, for anend-to-end motor vehicle status tracking and reporting system featuringimproved first notice of loss and machine-to-machine communicatingbetween the motor vehicle, the monitoring center, and the servicesoffering independent service providers (tow truck operators or claimsservicers, for illustrative non-limiting examples), and enhanced revenuefor insurance providers tracking motor vehicle status, incidents, andincident or accident reconstruction, documentation, and adjustment. Theimproved first notice of loss provided by the operation of the automatedcrash detection application 14 benefits insurance carriers, fleetoperators, and individual motor vehicle operators by identifying theinsured motorist or driver and the location of the incident involvingthe driver and the motor vehicle while providing coverage details toimprove claims processing efficiencies and advance the handling andresolution of claims though automatic or manual reporting of incidentoccurrences and communication to service providers of assistance needs.The system tracks and monitors vehicle care and logistics, while furtherassisting with evaluation of accident causes and reconstruction forresolution purposes.

The application 14 operates 52 in a background mode automatically orupon initiation by a driver and resolves locating insurance informationfrom a wallet or storage within the motor vehicle. Independent serviceproviders 22 such as tow truck operators benefit with automatedidentification of insured drivers, motor vehicle or incident location,and automatic or manual initiation of service support and response.Images of service response at the incident location are readily uploadedusing the lantern 24 and the video and telecommunications equipment 19of the service provider 22 to the monitoring center 18 to providedocumentation for service fees while potentially reducing claims againstservice providers. In the illustrated embodiment, the lantern 24 maycomprise imaging devices configured particularly for imaging (video andstill), storing the images with metadata (for example, location GPSinformation, date and time), and communicating the images directly orindirectly at a later time to the communications hub 186. Such devicesmay include a smart phone, a body camera, specially configured cameraimaging device, as well as one or more imaging devices mounted to aresponding tow vehicle.

Insurance claims servicers 26 obtain automated and seamlesscommunications of identified motorist claimants and improved timelyfirst notice of loss and further benefit with increased efficiency ofservices dispatch processing and handling of claims resolutionsincluding as appropriate access and uploading of live video and audiofrom incidents. Fleet (as well as individual) motor vehicles operated bydrivers registered with the central tracking/dispatch monitoring center18 are readily monitored, assisted and reported on appropriately.

The central communications hub 186 receives notice of the crash eventand provides early notice of loss to the insurance carrier 26 even priorto notice and/or claim by the insured. The system thereby filtersaccidents to provide assistance from the response servicer in the crashevent incidents that have significant possible damages (accidentsrequiring tow service are more likely to involve a subsequent claim tothe carrier for damages). While the number of such incidents is lessthan the “parking lot” or low impact incidents, the damage claims forsuch incidents are significantly more. The insurance carrier can thusdirect coordinated attention to reducing the administrative costs ofclaims resolution while collecting accident details, documents, andvideo and images, for possible use in litigation and in settlement aswell as analysis for roadway and motor vehicle defects. Promptresolution not only reduces costs to the insurance carrier but leads toincreased policyholder satisfaction. The communications hub 186 therebyprovides motor vehicle accident communications from first notice of lossto final resolution of claims and damages. The communications hub 186within the crash detection and reporting system 180 supports managementof claims and claims analysis, customer policyholder experiences, dataand documents collection and storage, as well as providing readilyascertainable status of the motor vehicle (storage, repair, salvage),and tracking of payments for repairs, parts, towing and storage fees,and claims for personal and property damage. The central repositorydatabase 190 makes claims and vehicle status and documents readilyavailable to the range of servicers while facilitating workflow and taskassignment communications, such as through application program interface(API) interfaces tailored to provide access to the particularinformation needed by a respective service provider.

More particularly described, the present invention provides acomprehensive crash event and claims servicing system with a centralizedcommunications hub for receiving, storing and distributing crash eventinformation for parties involved with the crash event. The comprehensivecrash event and claims servicing system comprises a telecommunicationsnetwork and a communications hub having a transceiver for receiving andcommunicating through the network crash event information from at leastone crash event servicer and maintaining said information in anelectronic database operatively engaged with the communications hub. Thecrash event notifier communicates notice of a possible crash event tothe communications hub to initiate a crash event file for maintainingcrash event information associated with a crash event. The crash eventfile is associated with an identifier associated with a notice ofpossible crash event for information collection, storage, anddistribution. The crash event notifier, or source providing notice of acrash event includes a crash event detector device such as the mobilecommunications device carried by the driver of the vehicle involved inthe possible crash event, a crash event SDK imbedded in a consumersoftware application operated by an insurance carrier, a motor clubservicer, a cell phone network provider, a motor vehicle OEM monitoringservicer, a telecommunications report, a towing dispatch servicer, and atowing service provider (private or municipal). In the illustratedembodiment, the crash event notifier comprises a mobile communicationsdevice configured with software instructions that upon executionmonitors for the occurrence of the possible crash event by periodicallyinterrogating (a) a motion signal of a sensor responsive to motion and(b) a sound signal of a sound sensor responsive to sound signals withina predetermined period matching the crash sound indicators. The crashsound indicators comprise one or more of (i) motor vehicle glassbreakage, (ii) metal folding, (iii) contact thud, and (iv) tiresscreeching. The crash event file may contain crash event informationgenerated prior to a claim being filed with an insurance carrier.

The notice of the possible crash event communicates from the crash eventnotifier electronically within the communications network, for example,via an API operative on a crash event detector or by direct data entryresulting from one of a phone call, a text message, or an electronicmail message.

The crash event servicer information may comprise a tow service providerwith crash event information that includes at least the service requesttime, dispatch tower ID, tow service driver, tow vehicle ID, and arrivaltime communicated through the network to the communications hub. Vehicledisposition information includes alternatively a motor vehicledisposition site for delivery by the tow service provider of anundrivable motor vehicle as instructed by the communications hub 186 andcrash event information including delivery date, time, and recipient ofthe undrivable motor vehicle to the motor vehicle disposition sitecommunicated through the network to the communications hub. The claimsservicer associated with an insurance carrier that provides insurancefor the undrivable motor vehicle communicates crash event informationthrough the network to the communications hub including policy holderidentification and disposition information for the undrivable motorvehicle. The motor vehicle disposition site comprises for example, arepair center for evaluating repair and repairing the undrivable motorvehicle, in response to instructions communicated from thecommunications hub by the claims servicer. Upon a determination ofsalvage, the claim servicer in consultation with the vehicle owner, maydirect transfer of the undrivable motor vehicle to a salvage yard andcommunicate such disposition as crash event information including date,time, and recipient of the undrivable motor vehicle to the salvage yardcommunicated through the network to the communications hub by the claimsservicer.

In an embodiment, the crash event information further comprises a crashevent notifier source identification, a motor vehicle identification, acrash event temporal information of date, time and location, a pluralityof crash event metadata comprising the motion signals, the crash soundsignals, and an algorithmic scoring of said signals, one or more crashresponse confirmations, recordings of telephone calls with emergencypolice services, confirmations of crash event communications initiatedto contacts including family, employer, and insurance providerservicers, motor vehicle tow response temporal information of time anddate of request, dispatch, arrival, departure from crash site, arrivalat vehicle disposition site, motor vehicle service provideridentification, tow vehicle identification.

Such information may be extracted from the source of the first notice ofloss event notifier. For example, the data may be most complete when theevent notice comes directly from the crash detection applicationoperative on the mobile communications device discussed above or from animbedded SDK. The extracted information includes the notice sourceidentifier for tracking and follow-up purposes, as appropriate a mobilecommunications device identifier, the vehicle identification (VINnumber), event temporal information including date, time and location,including for example, GPS information, crash metadata including but notlimited to, crash severity consisting of accelerometer, gyroscopic,audio and algorithmic scoring. The communications hub 186 furtherreceives and stores user crash confirmation responses, includingescalation levels, for example, evaluation and approvals of motorvehicle status, repair, parts order and delivery, salvage, anddisposition including transferor, receipt, and release by authorizedparties. Recorded emergency telephone calls, for example to local policeservices using a 911 number, may be retained within the records of thecommunications hub 186. Similarly, the communications hub 186 maintainsrecords regarding event communications to authorized contacts of theoperator, including communications initiated to family, employer, agentsor other appropriate individuals. Tow or other assistance requestsinformation may be maintained, including but not limited to the requesttime, dispatched tower ID, driver, vehicle ID, and arrival time. Othersources of information related to the crash event and its resolution maybe integrated as appropriate. For example, the comprehensive crash eventand claims servicing system may further comprise information as to thepolicyholder including name, address, phone number and electronic mailaddress, such as may be communicated to the communications hub by theclaims servicer. The insured information further includes at least onemotor vehicle information insured by the insurance carrier, includingfor each motor vehicle an associated VIN, license tag number, vehiclemake, vehicle model, vehicle year, and vehicle color; and insurancepolicy information including policyholder identification, a motorvehicle information number, the insurance carrier, the policy number,the insurance agent identifier, insurance coverage, and identificationof other drivers covered by the insurance policy. The other insureddrivers information including for each a name, address, one or morephone number including primary, cell phone, or office secondary,electronic mail address, one or more motor vehicles number; emergencycontacts information including name, relationship, and contact mode(telephone, email, SMS text). With reference to FIG. 11, the towvehicles operated by the service responder preferably are equipped withthe plurality of imaging devices 252 mounted and operated for providingimages of conditions in selected directions around the tow vehicle. Afirst embodiment provides respective imaging devices mounted for front,rear, and opposing lateral side images. Alternatively, the tow vehiclemay include in-cab imaging devices for imaging the operation of the towvehicle and/or outwardly for the travel or surroundings of the towvehicle. Such imaging devices typically include temporal data (date andtime) associated with the video imaging. The crash event informationfurther comprises respective videos and still pictures of the imagingdevices depicting (a) drive-up to the crash accident scene, (b) thedamaged vehicle and crash accident scene, and (c) towing processincluding loading at the crash site, intermediate transport, andunloading at the destination. Further, the crash event information mayinclude textual information about the damaged vehicle and the accidentscene, towed vehicle destination, and towed vehicle indentation.

Alternatively, imaged videos may be analyzed for determining anidentification of a “move over” violation by a passing motor vehicle.For example, accident scene information is derived from the mobilecommunications device configured with the accident detection applicationdiscussed above or embedded SDK, in-network video equipped tow trucksoperated by crash event responders, tow truck drivers equipped withimaging application software operable on smart phones or other mobilecommunication devices such as tablets, and audio messaging and/ortextual descriptions such as from the insured driver and the tow driver.

The disclosed communications hub 186 coordinates the processing of theinsurance claim and vehicle disposition information, which informationis derived by integrations to the data base, from the fleet bub or byother electronic means via appropriate APIs or by direct data entryresulting from phone calls, text messages, emails or other humaninterfaced means from the various persons, entities and servicesinvolved in the claims process. These include the policyholder, theinsurance agent, the repair facilities and salvage and auctionfacilities that receive the motor vehicle through instructions ofauthorized entities (typically, the motor vehicle owner in conjunctionwith the claims servicer), as well as towing services (which companiesmay be independent or networked within the disclosed comprehensive crashevent and claims servicing system, and including a two dispatchservice), insurance provider claims department or servicer, the claimsappraiser/adjuster, crash investigator and reconstruction services,medical services providers, temporary car or vehicle providers (carrental services), customer experience/customer service providers (suchas insurance provider or other agencies that interact between theservicer and the insured or driver).

The communications network of the comprehensive crash event and claimsservicing system provides communications facilities and protocols on abidirectional basis, to obtain data and claim status from all personsand entities involved in the crash/tow/claim solution, including but notlimited to, email, voicemail, video, SMS text, still frame photographs,and text rendered from audio narrative. The communications bub 186maintains and operates APIs to facilitate direct integration with claimsprocessing software already in place at the insurance company or othercrash/tow/claim entities. The claims processing servicer may grant theconsumer or selected crash/tow/claim participant access to portions ofthe communications hub database and information appropriate for therespective role in the claims solution process. The communications hub186 provides seamless network access to the database across multipledevices including computers, tablets and smart phones. The automated,programmable, work-flow infrastructure facilitates efficient processingof claims-related tasks, data management and communication requirementsamong all the participants in the crash/tow/claim solution for resolvingmotor vehicle accident event claims.

In that regard, the communications hub 186 further provides data andcommunications capabilities for the range of claims resolution functionsand services. The communications hub 186 supports a vehicle dispositiontriage center that may be used by the insurance services provider, or anauthorized third party entity, to review the real time videos, pictures,tow driver's comments, and crash event meta data in an evaluation of theclaims, for example, a determination whether the vehicle is a total lossor is repairable, and thus choose an appropriate destination for thedamaged vehicle transported from the accident site. The communicationshub 186 supports a tow vehicle monitoring center whereby the computerand video equipment on the tow trucks is periodically checked for properoperation, including dirty and inoperative cameras. This is particularlyuseful within networked tow service providers to maintaining standardsand quality. The collected information facilitates an automated processfor creating crash incident reports for use appropriate entities in thecrash/tow/claim solution. The communications hub supports periodicautomated quality checks of the crash detection application operated onthe mobile communications device or contained in an embedded SDK. Thevideos captured during the towing cycle proximate an accident scenesupports subsequent analysis of the capture of “move over” violations,to encourage increased safety to crash event responders at a crashaccident scene.

Computer networks suitable for use with the embodiments described hereininclude local area networks (LAN), wide area networks (WAN), Internet,or other connection services and network variations such as the worldwide web, the public internet, a private internet, a private computernetwork, a public network, a mobile network, a cellular network, avalue-added network, and the like. Computing devices coupled orconnected to the network may be any microprocessor-controlled devicethat permits access to the network, including terminal devices, such aspersonal computers, workstations, servers, mini computers, main-framecomputers, laptop computers, mobile computers, palm top computers, handheld computers, mobile phones, TV set-top boxes, or combinationsthereof. The computer network may include one of more LANs, WANs,Internets, and computers. The computers may serve as servers, clients,or a combination thereof.

The crash detection, response and reporting apparatus and method can bea component of a single system, multiple systems, and/or geographicallyseparate systems. The crash detection, response and reporting apparatusand method can also be a subcomponent or subsystem of a single system,multiple systems, and/or geographically separate systems. The crashdetection, response and reporting components can be coupled to one ormore other components (not shown) of a host system or a system coupledto the host system.

One or more components of the crash detection, response and reportingapparatus and method and/or a corresponding interface, system orapplication to which the crash detection, response and reportingapparatus is coupled or connected includes and/or runs under and/or inassociation with a processing system. The processing system includes anycollection of processor-based devices or computing devices operatingtogether, or components of processing systems or devices, as is known inthe art. For example, the processing system can include one or more of aportable computer, portable communication device operating in acommunication network, and/or a network server. The portable computercan be any of a number and/or combination of devices selected from amongpersonal computers, personal digital assistant devices, portablecomputing devices, and portable communication devices, but is not solimited. The processing system can include components within a largercomputer system.

The processing system of an embodiment includes at least one processorand at least one memory device or subsystem. The processing system canalso include or be coupled to at least one database. The term“processor” as generally used herein refers to any logic processingunit, such as one or more central processing units (CPUs), digitalsignal processors (DSPs), application-specific integrated circuits(ASIC), etc. The processor and memory can be monolithically integratedonto a single chip, distributed among a number of chips or components,and/or provided by some combination of algorithms. The methods describedherein can be implemented in one or more of software algorithm(s),programs, firmware, hardware, components, circuitry, in any combination.

The components of any system that include the crash detection, responseand reporting apparatus and method can be located together or inseparate locations. Communication paths couple the components andinclude any medium for communicating or transferring files among thecomponents. The communication paths include wireless connections, wiredconnections, and hybrid wireless/wired connections. The communicationpaths also include couplings or connections to networks including localarea networks (LANs), metropolitan area networks (MANs), wide areanetworks (WANs), proprietary networks, interoffice or backend networks,and the Internet. Furthermore, the communication paths include but arenot limited to, removable fixed mediums like floppy disks, hard diskdrives, and CD-ROM disks, as well as flash RAM, Universal Serial Bus(USB) connections, RS-232 connections, telephone lines, buses, andelectronic mail messages.

Aspects of the crash detection, response and reporting apparatus andcorresponding systems and methods described herein may be implemented asfunctionality programmed into any of a variety of circuitry, includingprogrammable logic devices (PLDs), such as field programmable gatearrays (FPGAs), programmable array logic (PAL) devices, electricallyprogrammable logic and memory devices and standard cell-based devices,as well as application specific integrated circuits (ASICs). Some otherpossibilities for implementing aspects of the crash detection, responseand reporting apparatus and method and corresponding systems and methodsinclude: microcontrollers with memory (such as electronically erasableprogrammable read only memory (EEPROM)), embedded microprocessors,firmware, software, etc. Furthermore, aspects of the crash detection,response and reporting apparatus and method and corresponding systemsand methods may be embodied in microprocessors having software-basedcircuit emulation, discrete logic (sequential and combinatorial), customdevices, fuzzy (neural) logic, quantum devices, and hybrids of any ofthe above device types. Of course, the underlying device technologiesmay be provided in a variety of component types, e.g., metal-oxidesemiconductor field-effect transistor (MOSFET) technologies likecomplementary metal-oxide semiconductor (CMOS), bipolar technologieslike emitter-coupled logic (ECL), polymer technologies (e.g.,silicon-conjugated polymer and metal-conjugated polymer-metalstructures), mixed analog and digital, etc.

It should be noted that any system, method, and/or other componentsdisclosed herein may be described using computer aided design tools andexpressed (or represented), as data and/or instructions embodied invarious computer-readable media, in terms of their behavioral, registertransfer, logic component, transistor, layout geometries, and/or othercharacteristics. Computer-readable media in which such formatted dataand/or instructions may be embodied include, but are not limited to,non-volatile storage media in various forms (e.g., optical, magnetic orsemiconductor storage media) and carrier waves that may be used totransfer such formatted data and/or instructions through wireless,optical, or wired signaling media or any combination thereof. Examplesof transfers of such formatted data and/or instructions by carrier wavesinclude, but are not limited to, transfers (uploads, downloads, e-mail,etc.) over the Internet and/or other computer networks via one or moredata transfer protocols (e.g., HTTP, FTP, SMTP, etc.). When receivedwithin a computer system via one or more computer-readable media, suchdata and/or instruction-based expressions of the above describedcomponents may be processed by a processing entity (e.g., one or moreprocessors) within the computer system in conjunction with execution ofone or more other computer programs.

Unless the context clearly requires otherwise, throughout thedescription and the claims, the words “comprise,” “comprising,” and thelike are to be construed in an inclusive sense as opposed to anexclusive or exhaustive sense; that is to say, in a sense of “including,but not limited to.” Words using the singular or plural number alsoinclude the plural or singular number respectively. Additionally, thewords “herein,” “hereunder,” “above,” “below,” and words of similarimport, when used in this application, refer to this application as awhole and not to any particular portions of this application. When theword “or” is used in reference to a list of two or more items, that wordcovers all of the following interpretations of the word: any of theitems in the list, all of the items in the list and any combination ofthe items in the list.

The above description of embodiments of the crash detection, responseand reporting apparatus and method and the corresponding systems andmethods is not intended to be exhaustive or to limit the systems andmethods to the precise forms disclosed. While specific embodiments of,and examples for, the crash detection, response and reporting apparatusand method and corresponding systems and methods are described hereinfor illustrative purposes, various equivalent modifications are possiblewithin the scope of the systems and methods, as those skilled in therelevant art will recognize. The teachings of the crash detection,response and reporting apparatus and method and corresponding systemsand methods provided herein can be applied to other systems and methods,not only for the systems and methods described above.

The elements and actions of the various embodiments described above canbe adapted, modified, and combined to provide further embodiments inaccordance with the present invention of the crash detection, responseand reporting apparatus and methods and corresponding systems andmethods in light of the above detailed description. While this inventionhas been described in detail with particular reference to illustrative,non-limiting embodiments thereof, the principles and modes of operationof the present invention have been described in the foregoingspecification. The invention is not to be construed as limited to theparticular forms disclosed because these are regarded as illustrativerather than restrictive. Moreover, those skilled in the art may makemodifications, variations and changes thereto without departure from thespirit and scope of the invention as described by the following claims.

What is claimed is:
 1. A communications hub providing a repository forresolution of undrivable motor vehicle crash events, comprising: aplurality of mobile communications devices, each associated with arespective one of the plurality of drivers and configured with a sensorthat generates a motion signal responsive to motion of the mobilecommunications device and a sound receiver for receiving a sound signalof sound proximate the mobile communications device; the mobilecommunications device configured with software instructions that uponexecution monitors for an occurrence of a crash event by periodicallyinterrogating (a) the motion signal to determine whether a change inmotion exceeds a predetermined motion threshold and or (b) the soundsignal to determine whether a sequence of sensed sound signals within apredetermined period matches one or more crash sound indicators of (i)glass breakage, (ii) metal folding, (iii) contact thud, and (iv) tiresscreeching; each mobile communications device comprising a display thatupon determining the occurrence of the crash incident displays apossible event window for selection of one of (a) to return the mobilecommunications device to monitoring for the occurrence of the crashincident and (b) to confirm the crash incident; the mobilecommunications device, upon (a) confirmation of the crash incident or(b) upon a failure of selection of one of the selectable options withina predetermined period, the mobile communications device communicatingby a communications network an identifier associated with the mobilecommunications device and crash incident information of a location data,date and time to the tracking and dispatch center; the tracking anddispatch center having a computer processor configured with anelectronic memory device that maintains driver information of drivername, address, insurance servicer and policy number for each of theplurality of drivers and further comprising for each mobilecommunications device a repository of: vehicle crash incidentinformation communicated by the mobile communications device andassociated with a motor vehicle; and one or more vehicle crash datarecords, each said vehicle crash record containing data provided by oneof a plurality of crash event servicers; the plurality of crash eventservicers comprising: (i) at least one response servicer for dispatchingby the tracking and dispatch center to a site of the crash incidentbased on the location data, the response servicer providing an imagingdevice and a communications device, whereby images received by theimaging device communicate by the communications device through thenetwork to the tracking and dispatch center for recording in therepository; and (ii) a claims servicer that receives from the trackingand dispatch center notice of the identifier and crash incidentinformation, the claims service center configured for servicing aninsurance claim arising from the crash event using the vehicle crashincident information and the vehicle crash data records communicated tothe tracking and dispatch center and recorded in the repository.
 2. Thecommunications hub as recited in claim 1, further comprising a secureportal for access by the plurality of crash event servicers forcommunicating motor vehicle data for entry to the repository.
 3. Thecommunications hub as recited in claim 2, wherein the plurality of crashevent servicers further comprises a repair servicer for receiving themotor vehicle involved in the crash event, whereby the motor vehicle isevaluated for possible repair, which disposition and evaluation iscommunicated to the repository.
 4. The communications hub as recited inclaim 3, wherein the repair servicer is one of a plurality of repairservicers that are affiliated by the claims servicers for the receipt,evaluation, and repair of motor vehicles.
 5. The communications hub asrecited in claim 3, further comprising a parts supplier for distributionof motor vehicle repair parts to the repair servicer, which distributionis communicated to the repository.
 6. The communications hub as recitedin claim 2, wherein the plurality of crash event servicers furthercomprises a salvage facility for receiving the motor vehicle upon adetermination of unreparability, which disposition is communicated tothe repository.
 7. The communications hub as recited in claim 2, whereinthe plurality of crash event servicers further comprises a motor vehiclerental servicer for providing temporary use of a rental motor vehicleduring resolution of the damages claim by the claims servicer, wherebythe providing of the rental motor vehicle is communicated to therepository.
 8. The communications hub as recited in claim 1, wherein theplurality of crash event servicers further comprises an insurance agencythat provides insurance services to at least one of the plurality ofdrivers.
 9. The communications hub as recited in claim 1, wherein thedriver information further comprises one or more contact identifiers,each said one or more contact identifiers for a contact personassociated with a respective one of the plurality of drivers; andfurther comprising the computer processor configured to contact saidrespective contact person based on the one or more contact identifiers,which contact communication is communicated to the repository.
 10. Thecommunications hub as recited in claim 2, wherein the plurality of crashevent servicers further comprises a motor vehicle accidentreconstruction service for engineering analysis of the crash event,whereby the engineering analysis is communicated to the repository. 11.The communications hub as recited in claim 1, wherein the responseservicer further provides a vehicle transporter, whereby the crashedmotor vehicle may be transported from the crash location.
 12. Thecommunications hub as recited in claim 1, wherein the imaging device isoperable selectively for video and for single frame images.
 13. Thecommunications hub as recited in claim 1, wherein the sensor comprisesan accelerometer that generates an acceleration signal as indicative ofthe motion of the mobile communications device.
 14. The communicationshub as recited in claim 1, wherein the sensor comprises a gyroscope thatgenerates an angular rotation signal as indicative of the motion of themobile communications device.
 15. The communications hub as recited inclaim 1, wherein the imaging device of the response servicer iswireless.
 16. The communications hub as recited in claim 1, wherein themobile communications device further comprising an electronic memorydevice configured for receiving and storing crash incident informationof the motion signal and the crash sound signals for a predeterminedperiod preceding the possible crash event.
 17. The communications hub asrecited in claim 16, further comprising the continuous recordingdatabase maintaining a trailing portion for a second predeterminedperiod after the possible crash event.
 18. The communications hub asrecited in claim 1, wherein the mobile communications device isconfigured to interrogate both the motion signal and the crash soundsignal in determining whether an occurrence of a possible crash eventoccurred based on the change in motion exceeding the predeterminedmotion threshold and the crash sound signal matches one or more of crashsound indicators of (i) glass breakage, (ii) metal folding, (iii)contact thud, and (iv) tires screeching.
 19. The communications hub asrecited in claim 1, wherein the mobile communications device configuredfor generating video files imaging the crash event automatically uponthe failure of the selection of one of the selectable options orselectively after confirmation of the crash event, said video filescommunicated to the tracking and dispatch center.
 20. The communicationshub as recited in claim 1, wherein the mobile communication devicesfurther configured, upon failure to respond within the firstpredetermined period, for making a second alert with the mobilecommunications device for a response within a second predeterminedperiod to (i) return to monitoring or (ii) to confirm the possible crashevent.
 21. The communications hub as recited in claim 20, wherein thesecond alert comprises communicating an audible message as to thepossible crash event and the response comprises a selectable voiceoption (i) to return monitoring or (ii) to confirm the possible crashevent.
 22. A comprehensive crash event and claims servicing system,comprising: a telecommunications network; a communications hub having atransceiver for receiving and communicating through the network crashevent information from at least one crash event servicer and maintainingsaid crash event information in an electronic database operativelyengaged with the communications hub; a crash event notifier thatcommunicates a notice of a crash event to the communications hub toinitiate a crash event file for maintaining the crash event informationassociated with the crash event, wherein the crash event notifiercomprises one of a crash event detector device, a crash event SDKimbedded in a consumer software application operated by an insurancecarrier, a motor club servicer, a cell phone network provider, a motorvehicle OEM monitoring servicer, a telecommunications report, a towingdispatch servicer, and a towing service provider (private or municipal);and said crash event file associated with an identifier associated withthe notice of the crash event, whereby said crash event informationbeing accessible for resolution of personal and property claims arisingfrom the crash event.
 23. The comprehensive crash event and claimsservicing system as recited in claim 22, wherein said crash eventdetector device comprises a mobile communications device configured withsoftware instructions that upon execution monitors for the occurrence ofthe crash event by periodically interrogating (a) a motion signal of asensor responsive to motion and (b) a sound signal of a sound sensorresponsive to sound signals within a predetermined period matching crashsound indicators.
 24. The comprehensive crash event and claims servicingsystem as recited in claim 23, wherein the crash sound indicatorscomprise one or more of (i) motor vehicle glass breakage, (ii) metalfolding, (iii) contact thud, and (iv) tires screeching.
 25. Thecomprehensive crash event and claims servicing system as recited inclaim 22, wherein said crash event file contains crash event informationgenerated prior to a claim being filed with an insurance carrier. 26.The comprehensive crash event and claims servicing system as recited inclaim 22, wherein the notice of the crash event communicateselectronically via an API operative on a crash event detector or bydirect data entry resulting from one of a phone call, a text message, oran electronic mail message.
 27. The comprehensive crash event and claimsservicing system as recited in claim 22, wherein said crash eventservicer further comprises: a tow service provider with crash eventinformation including at least service request time, dispatch tower ID,tow service driver, tow vehicle ID, and arrival time communicatedthrough the network to the communications hub; and a motor vehicledisposition site for delivery by the tow service provider of anundrivable motor vehicle as instructed by the communications hub andcrash event information including delivery date, time, and recipient ofthe undrivable motor vehicle to the motor vehicle disposition sitecommunicated through the network to the communications hub; and a claimsservicer associated with an insurance carrier providing insurance forthe undrivable motor vehicle and communicating crash event informationthrough the network to the communications hub including policy holderidentification and disposition information for the undrivable motorvehicle.
 28. The comprehensive crash event and claims servicing systemas recited in claim 27, wherein the motor vehicle disposition sitecomprises a repair center for evaluating repair and repairing theundrivable motor vehicle, in response to instructions communicated fromthe communications hub by the claims servicer.
 29. The comprehensivecrash event and claims servicing system as recited in claim 28, furthercomprising a salvage yard and communicating crash event informationincluding date, time, and recipient of the undrivable motor vehicle tothe salvage yard communicated through the network to the communicationshub by the claims servicer.
 30. The comprehensive crash event and claimsservicing system as recited in claim 27, wherein the crash eventdetector device comprises a mobile telecommunications device configuredwith software instructions that upon execution monitors for anoccurrence of a crash event by periodically interrogating (a) the motionsignal to determine whether a change in motion exceeds a predeterminedmotion threshold and or (b) the sound signal to determine whether asequence of sensed sound signals within a predetermined period matchescrash sound indicators of one or more of (i) motor vehicle glassbreakage, (ii) metal folding, (iii) contact thud, and (iv) tiresscreeching.
 31. The comprehensive crash event and claims servicingsystem as recited in claim 27, wherein crash event information furthercomprises a crash event notifier source identification, a motor vehicleidentification, a crash event temporal information of date, time andlocation, a plurality of crash event metadata comprising the motionsignals, the sound signals, and an algorithmic scoring of said signals,one or more crash response confirmations, recordings of telephone callswith emergency police services, confirmations of crash eventcommunications initiated to registered related contacts, motor vehicletow response temporal information of time and date of request, dispatch,arrival, departure from crash site, arrival at vehicle disposition site,motor vehicle service provider identification, tow vehicleidentification.
 32. The comprehensive crash event and claims servicingsystem as recited in claim 27, wherein said crash event informationfurther comprises: policyholder information including name, address,phone number and electronic mail address communicated to thecommunications hub by the claims servicer; at least one motor vehicleinformation insured by the insurance carrier, including for each motorvehicle an associated VIN, license tag number, vehicle make, vehiclemodel, vehicle year, and vehicle color; and insurance policy informationincluding policyholder identification, a motor vehicle informationnumber, the insurance carrier, the policy number, the insurance agentidentifier, insurance coverage, and identification of other driverscovered by the insurance policy.
 33. The comprehensive crash event andclaims servicing system as recited in claim 32 wherein said otherinsured drivers information including for each a name, address, one ormore phone number including primary, cell phone, or office secondary,electronic mail address, one or more motor vehicles number; emergencycontacts information including name, relationship, and contact mode(telephone, email, SMS text).
 34. The comprehensive crash event andclaims servicing system as recited in claim 27, wherein said tow vehicleof said tow service provider further comprises a plurality of imagingdevices mounted on said tow vehicle for providing images imaged by saidrespective imaging devices; and said crash event information furthercomprises respective videos and still pictures of the imaging devicesdepicting (a) drive-up to the crash accident scene, (b) the damagedvehicle and crash accident scene, (c) towing process including loadingand unloading at the destination.
 35. The comprehensive crash event andclaims servicing system as recited in claim 34, wherein said crash eventinformation further comprises textual information about the damagedvehicle and the accident scene, towed vehicle destination, and towedvehicle identification.
 36. The comprehensive crash event and claimsservicing system as recited in claim 34, wherein the imaged videos areanalyzed for determining an identification of a “move over” violation bya passing motor vehicle.
 37. A method of resolving claims arising fromundrivable motor vehicle crash events via a communications hubrepository service, comprising the steps of: (a) providing a pluralityof mobile communications devices, each associated with a respective oneof the plurality of drivers and configured with a sensor that generatesa motion signal responsive to motion of the mobile communications deviceand a sound receiver for receiving a sound signal of sound proximate themobile communications device; (b) configuring the mobile communicationsdevice with software instructions that upon execution monitors for anoccurrence of a crash event by periodically interrogating (i) the motionsignal to determine whether a change in motion exceeds a predeterminedmotion threshold and or (b) the sound signal to determine whether asequence of sensed sound signals within a predetermined period matchescrash sound indicators of one or more of (i) motor vehicle glassbreakage, (ii) metal folding, (iii) contact thud, and (iv) tiresscreeching; (c) upon determining by a respective mobile communicationsdevice the occurrence of the crash incident, displaying thereon apossible event window for selection of one of (i) to return the mobilecommunications device to monitoring for the occurrence of the crashincident and (ii) to confirm the crash incident; (d) upon (i)confirmation of the crash incident or (ii) upon a failure of selectionof one of the selectable options within a predetermined period,communicating by the mobile communications device within acommunications network an identifier associated with the mobilecommunications device and crash incident information of a location data,date and time to a tracking and dispatch center having a computerprocessor configured with an electronic memory device that maintainsdriver information of driver name, address, insurance servicer andpolicy number for each of the plurality of drivers; (e) receiving andstoring in a repository of the tracking and dispatch center, vehiclecrash incident information communicated by the mobile communicationsdevice and associated with the motor vehicle; and one or more vehiclecrash data records, each said vehicle crash record containing dataprovided by one of a plurality of crash event servicers; the pluralityof crash event servicers comprising: (i) at least one response servicerfor dispatching by the tracking and dispatch center to a site of thecrash incident based on the location data, the response servicerproviding an imaging device and a communications device; and (ii) aclaims servicer; (f) communicating by the communications device imagesreceived by the imaging device through the network to the tracking anddispatch center for recording in the repository; and (g) servicing bythe claims service center an insurance claim arising from the crashevent using the vehicle crash incident information and the vehicle crashdata records communicated to the tracking and dispatch center andrecorded in the repository.
 38. A method of servicing claims with acomprehensive crash event and claims servicing system, comprising thesteps of: (a) providing a telecommunications network; (b) establishing acommunications hub with a transceiver for receiving and communicatingthrough the network crash event information from at least one crashevent servicer and maintaining said crash event information in anelectronic database operatively engaged with the communications hub; (c)communicating from a crash event notifier that upon determination of acrash event, notice of the crash event to the communications hub toinitiate a crash event file for maintaining the crash event informationassociated with the crash event, said crash event file associated withan identifier associated with the notice of the crash event, wherein thecrash event notifier comprises one of a crash event detector device, acrash event SDK imbedded in a consumer software application operated byan insurance carrier, a motor club servicer, a cell phone networkprovider, a motor vehicle OEM monitoring servicer, a telecommunicationsreport, a towing dispatch servicer, and a towing service provider(private or municipal); and (d) providing access to said crash eventinformation for resolution of personal and property claims arising fromthe crash event.
 39. The method of servicing claims as recited in claim38, wherein the notice of the crash event communicates electronicallyvia an API operative on a crash event detector or by direct data entryresulting from one of a phone call, a text message, or an electronicmail message.
 40. A comprehensive crash event and claims servicingsystem, comprising: a telecommunications network; a communications hubhaving a transceiver for receiving and communicating through the networkcrash event information from at least one crash event servicer andmaintaining said crash event information in an electronic databaseoperatively engaged with the communications hub; a crash event notifierthat communicates notice of a crash event to the communications hub toinitiate a crash event file for maintaining the crash event informationassociated with the crash event; and said crash event file associatedwith an identifier associated with the notice of the crash event andcontains crash event information generated prior to a claim being filedwith an insurance carrier, whereby said information being accessible forresolution of personal and property claims arising from the crash event.41. A comprehensive crash event and claims servicing system, comprising:a telecommunications network; a communications hub having a transceiverfor receiving and communicating through the network crash eventinformation from at least one crash event servicer and maintaining saidcrash event information in an electronic database operatively engagedwith the communications hub; a crash event notifier that communicatesnotice of a crash event to the communications hub to initiate a crashevent file for maintaining crash event information associated with thecrash event; wherein the notice of the crash event communicateselectronically via an API operative on a crash event detector or bydirect data entry resulting from one of a phone call, a text message, oran electronic mail message; and said crash event file associated with anidentifier associated with the notice of the crash event, whereby saidcrash event information being accessible for resolution of personal andproperty claims arising from the crash event.
 42. A comprehensive crashevent and claims servicing system, comprising: a telecommunicationsnetwork; a communications hub having a transceiver for receiving andcommunicating through the network crash event information from at leastone crash event servicer and maintaining said crash event information inan electronic database operatively engaged with the communications hub;a crash event notifier that communicates notice of a possible crashevent to the communications hub to initiate a crash event file formaintaining the crash event information associated with the crash event;and said crash event file associated with an identifier associated withthe notice of the crash event, wherein said one or more crash eventservicer further comprises: a tow service provider with crash eventinformation including at least service request time, dispatch tower ID,tow service driver, tow vehicle ID, and arrival time communicatedthrough the network to the communications hub; a motor vehicledisposition site for delivery by the tow service provider of anundrivable motor vehicle as instructed by the communications hub andcrash event information including delivery date, time, and recipient ofthe undrivable motor vehicle to the motor vehicle disposition sitecommunicated through the network to the communications hub; and a claimsservicer associated with an insurance carrier providing insurance forthe undrivable motor vehicle and communicating crash event informationthrough the network to the communications hub including policy holderidentification and crash event information for the undrivable motorvehicle, whereby said crash event information being accessible forresolution of personal and property claims arising from the crash event.